Commits 1. Commit message Build skipList before exclude enrichment in apply section uses sentence-case plain format, but the change is scoped to one system (the workflow processor in internal/impl/pure/). Per repo convention (see prior commit deps: update OTEL package...), scoped changes should use system: message or system(subsystem): message format with a lowercase imperative verb, e.g. processor(workflow): fix skip list ordering when apply and skipped overlap. The wording is also somewhat unclear (exclude enrichment in apply section). Review The fix reorders skipFromMeta so the skipped set is populated before apply is processed, making apply authoritative when both are present (a stage listed in apply now runs even if it also appears in skipped). The behavior when apply is absent is unchanged. The added test case covers the new overlap scenario. LGTM

Commits

1. Commit message Build skipList before exclude enrichment in apply section uses sentence-case plain format, but the change is scoped to one system (the workflow processor in internal/impl/pure/). Per repo convention (see prior commit deps: update OTEL package...), scoped changes should use system: message or system(subsystem): message format with a lowercase imperative verb, e.g. processor(workflow): fix skip list ordering when apply and skipped overlap. The wording is also somewhat unclear ("exclude enrichment in apply section").

Review

The fix reorders skipFromMeta so the skipped set is populated before apply is processed, making apply authoritative when both are present (a stage listed in apply now runs even if it also appears in skipped). The behavior when apply is absent is unchanged. The added test case covers the new overlap scenario.

LGTM